SD - Surya - Venkat - Prudvi - 2016-06-01 - 27295 - Spec - Carrier Account Validation (Dan by 2016-07-06) #OrderEntry #US #abapexit
SPECIFICATIONS
27295 - Spec - Carrier Account Validation
Purpose
Carrier Account Validation
Admin Info
Purpose
|
Carrier Account Validation
|
Requested By
|
Dan Brennan
|
Spec Created By
|
Surya Basa
|
Spec Created Date
|
02/06/2016
|
Spec QA by
|
Venkat Kondapally
|
Objects
|
MV45AFZZ
|
Document Status
|
Completed
|
Estimates
Sl.No
|
Activity
|
Estimation in Hours
|
1
|
Research
|
20
|
2
|
Documentation
|
08
|
3
|
Development/ Config
|
44
|
4
|
Unit test in DEV
|
20
|
5
|
Unit test in QUA
|
20
|
6
|
Other activity
|
|
|
TOTAL
|
112
|
References
Prior Tickets
[Provide links of prior associated Spec / Break Fix BOSS document(s)]
Documents
[Attach any document(s) received for the requirement(s)]
FSDE - Carrier Account Validation.docx
Spec Changes
[List the changes made to program after the approval of the original requirement along with the Date on which the change request was received and the name of the initiator]
Sl.
|
Change Details
|
Requested By
|
Requested On
|
Notes if any
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Functional Requirement
Purpose/WHY:
[Explain the purpose of the project and the reason why this requirement has come]
Update the sales order user-exit to trigger an in-completion if the carrier account does not match the carrier code.
In Scope:
[List the
activities to be included in scope]
The functionality is restricted to standard orders (ZOR) both manual and EDI.
Out of Scope:
[Out of scope activities]
1. Order types not mentioned above are out of scope (e.g. contracts)
2. Change logs on the Ztable.
Solution Summary
[Discuss this section with Requester and get approval prior to beginning work]
Config:
Set up in-completion field as Description (sales order header) to standard order header. The field is not visible at the document level for sales orders, however it is visible in case of contracts which is out of scope.
Development:
1. Create a Ztable as below-
Cust. Grp. 2
|
Carrier
|
Description
|
Acct. # Length
|
059
|
FedEx
|
2 Day Air
|
9
|
060
|
FedEx
|
3 Day Air
|
9
|
061
|
FedEx
|
FedEx First Overnight
|
9
|
062
|
FedEx
|
Ground
|
9
|
063
|
FedEx
|
International 3 Day
|
9
|
064
|
FedEx
|
International 5 Day
|
9
|
066
|
FedEx
|
International Next Flight
|
9
|
067
|
FedEx
|
FedEx Priority
|
9
|
068
|
FedEx
|
Saturday
|
9
|
069
|
FedEx
|
Standard
|
9
|
195
|
UPS
|
2 Day Air AM
|
6
|
196
|
UPS
|
2 Day Air
|
6
|
197
|
UPS
|
3 Day Air
|
6
|
198
|
UPS
|
Ground
|
6
|
199
|
UPS
|
International 3 Day
|
6
|
200
|
UPS
|
International 5 Day
|
6
|
201
|
UPS
|
International 7 Day
|
6
|
202
|
UPS
|
Next Day AM
|
6
|
203
|
UPS
|
Next Day Air
|
6
|
204
|
UPS
|
Next Day Air
|
6
|
205
|
UPS
|
Next Day Saver
|
6
|
206
|
UPS
|
Saturday
|
6
|
207
|
UPS
|
UPS Sonic Air
|
6
|
2. Code in the sales order user exit to check the following conditions and trigger an in-completion -
This user-exit should trigger an incompletion in the following scenarios:
a) Incoterm is TPB, carrier doesn't match with table but match with account # length in text field.
b) Incoterm is TPB , carrier doesn't match with table and the account # text is missing in the header text.
c) Incoterm is TPB, carrier match with table but doesn't match with account # length in text field.
a) Incoterm is TPB and missing Account # in header text.
b Incoterm is TPB and Carrier (Cust. Grp. 2) does not match Account # length in text field (Note – in-completion should only trigger if carrier code is maintained in custom table above)
c) Incoterm is PPI and Account # is showing in text field
3. Customer Gr2 field is the key field.
4. Table entries should be validated.
5. User exit will trigger on "Description" field. This field will be blank and in-completion will trigger when there's a mismatch, otherwise the field will be filled with an "X".
SO
|
|
ZTable
|
Incoterm
|
Carrier
|
Text
|
Carrier
|
Text Length Match
|
Incompletion
|
TPB
|
Yes
|
No
|
Yes
|
NA
|
Yes
|
TPB
|
Yes
|
No
|
No
|
NA
|
No
|
TPB
|
Yes
|
Yes
|
Yes
|
No
|
Yes
|
TPB
|
Yes
|
Yes
|
Yes
|
Yes
|
No
|
TPB
|
Yes
|
Yes
|
No
|
NA
|
Yes
|
PPI
|
Yes
|
No
|
Yes
|
NA
|
Yes
|
PPI
|
Yes
|
No
|
No
|
NA
|
No
|
PPI
|
Yes
|
Yes
|
Yes
|
No
|
Yes
|
PPI
|
Yes
|
Yes
|
Yes
|
Yes
|
Yes
|
PPI
|
Yes
|
Yes
|
No
|
No
|
Yes
|
Test Plan
[List test scenarios/cases to be executed here]
NEC:
No.
|
Test Scenario
|
Expected Results
|
1
|
Create sales order with Incoterms not equal to PPI or TPB
|
No in-completion should trigger
|
2
|
Create a sales order with Incoterms PPI and no account # in text field
|
No in-completion should trigger
|
3
|
Create a sales order with Incoterms PPI and account # in text field
|
In-completion should trigger
|
4
|
Create a sales order with Incoterms TPB for carrier not contained in custom table
|
No in-completion should trigger
|
5
|
Create a sales order with Incoterms TPB and a match in custom table
|
No in-completion should trigger
|
6
|
Create a sales orders with Incoterms TPB, a carrier entry in the custom table, and no account # in the text field
|
In-completion should trigger
|
7
|
Create a sales order with Incoterms TPB, a carrier entry in the custom table, and a mismatched account # in the text field
|
In-completion should trigger
|
8
|
Update incomplete sales order (modify account # text to match carrier code)
|
In-completion should be removed
|
BMS ZTable:
Test Id
|
Test Scenario
|
Expected Results
|
SD001
|
Enter a valid carrier
|
Entry should be created
|
SD002
|
Enter an invalid carrier
|
Error should be displayed
|
SD003
|
Enter a duplicate value
|
Error should be displayed
|
SD004
|
Enter more than 2 digits in the length field
|
Error should be displayed
|
BMS User Exit:
Test Id
|
Test Scenario
|
Expected Results
|
SD001
|
Create ZOR order in such a way to trigger an in-completion (NEC3); remove the in-completion and save
|
The document should be completed
|
SD002
|
Make changes to the above order by changing the character length of header text
|
In-completion should trigger
|
SD003
|
Fix the character length on the above order.
|
In-completion should be removed
|
SD004
|
Create a ZOR order using a standard in-completion field (pay terms) and a mismatch of table entry (NEC3)
|
In-completion should trigger on two fields
|
SD005
|
Update pay terms on the above order.
|
In-completion should trigger on carrier validation
|
SD006
|
Update the Header text by making it blank.
|
In-completion should be removed
|
SD007
|
Create ZOR order with carrier 059 and header text with length 9 char and a blank in-between
|
In-completion should trigger
|
SD008
|
Create an EDI ZOR order; repeat SD004, SD005, SD006
|
In-completion should trigger on two fields
In-completion should trigger on carrier validation
In-completion should be removed
|
SD009
|
Run E2E cycle for the above created completed documents
|
Accounting documents should be posted
|
Solution Details
[Provide complete technical details for configuration or programming here]
Production Issue Solution
1. The exit was reverted to the previous version w/o the carrier enhancement and also the In-completion procedure was updated by removing the "Description" field.
2. The TR's were moved to NEP
3. 241 orders had the expected price issue of which deliveries were created for 28 orders. The information was provided to NEC.
Issues
[List Issues / Bugs identified in configuration or development]
1. Bug was identified in QUA testing and the same was fixed and tested in DEV.
2. The initial config and development TR's were moved to NEP on 7/14. The issue was reported on 7/15 in NEP. NEC was informed of the missing TR on 7/15.
3. On 7/20 the expected price issue was reported. Though the expected price (JED1) was different from Net Price (NETP) the document didn't show in-completion and also V.25 report didn't bring this order up for release.